chore(deps): align QPK pin to 9bb8f31e898e - #96
Conversation
Automated downstream QPK pin update after QPK_PIN landed on main. Co-Authored-By: Claude <noreply@anthropic.com>
🤖 Codex PR Review✅ Merge allowed: No issues found Review by Codex PR Review bot • PR |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7b3c87639e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| dependencies = [ | ||
| "pandas>=2.0", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@335c7a22bc3f570bd5705427ccc40172eda6b289", | ||
| "quant-platform-kit @ git+https://github.com/QuantStrategyLab/QuantPlatformKit.git@9bb8f31e898ea238a6446472f9f5e58133128d0c", |
There was a problem hiding this comment.
Align the drift workflow with the QPK bump
In scheduled or manually dispatched drift runs, this package now declares QPK@9bb8 here, but the reusable drift workflow is still pinned to QPK@335c7a22 in .github/workflows/drift-check.yml:17 and the test assertion in tests/test_drift_workflow_config.py:7 still locks in that stale ref. That leaves drift monitoring executing the old lifecycle workflow while installs/compat metadata point at the new QPK revision, so the monitoring path can miss the 9bb8 lifecycle fixes and diverge from the runtime version this bump is meant to validate. Please update the workflow pin and its assertion in the same dependency bump.
Useful? React with 👍 / 👎.
|
Superseded by the current QPK manifest target fdae6666ba4e; the matching replacement PR remains open. |
Summary
9bb8f31e898euv.lock,同步刷新 lockfileTest plan
🤖 Generated with Claude Code